Technical Communication
Work in the IT field has always been opaque to those outside it. As the rate of technological change and adoption increases - it becomes all the more important to understand the dichotomy between technical and business stakeholders, and to address the risks that failed communication can bring.
A close colleague of mine delivered an astute line to me recently as I went on a diatribe about how a silly decision was made which ignored advice provided by the technical team members. He said:
Communication exists to drive an outcome. If the outcome you want isn’t being realised, your communication strategy needs to change.
This seems almost too obvious after the fact - and a little simplistic - _“If you aren’t getting what you need, say it in french!“. The reductio ad absurdum argument is however a little facetious here: and doesn’t dive into what I see as some core problematic realities that need to be addressed.
The Skillset Divide
Incentives and Decision Makers
Real-World Example
Final Thoughts
…as I write this